-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable feature to fix unstabilized #[bench]
#26
Conversation
This will cause this crate to become nightly only, #25 is a better fix that will still allow building on stable 1.38+. |
Inspired by the fix in cargo, missed the one you linked. Feel free to close if that one gets merged. |
ping @alexcrichton |
yeah if rust-lang/cargo#7198 was the inspiration, that's just tests... |
Sorry, but I am no longer maintaining this crate. |
But who is? Perhaps it should be transferred to rustasync since it is used by tide? |
We'd be happy to help share the maintenance burden if there's help needed! |
I guess route-recognizer is no longer maintained? My PR: http-rs/route-recognizer#25 Comment from Alex Crichton: http-rs/route-recognizer#26 (comment)
I guess route-recognizer is no longer maintained? My PR: http-rs/route-recognizer#25 Comment from Alex Crichton: http-rs/route-recognizer#26 (comment)
closes iron#148 - use patch for route-recognizer - add `dyn` to trait objects I guess route-recognizer is no longer maintained? My PR: http-rs/route-recognizer#25 Comment from Alex Crichton: http-rs/route-recognizer#26 (comment)
closes iron#148 - use patch for route-recognizer - add `dyn` to trait objects I guess route-recognizer is no longer maintained? My PR: http-rs/route-recognizer#25 Comment from Alex Crichton: http-rs/route-recognizer#26 (comment)
rust-lang/rust#62507